Secure messaging systems and methods

ABSTRACT

Systems and methods for secure messaging and automation are disclosed herein. An example method includes providing, by an application server layer, a user-facing application that accesses a data retention system and a predictive analytics system through a web services layer, the user-facing application being secured through use of a security token cached on a web browser that provides the user-facing application, establishing a security protocol or security token utilized between the application server layer and the web services layer that is different from the security token cached on the web browser; and performing asynchronous processing based on user interaction with a goal-based planning application that processes data from a plurality of user accounts.

FIELD OF THE TECHNOLOGY

The present technology relates generally to secure messaging, and more particularly, but not by limitation, to systems and methods for secure messaging that allow modular subsystem isolation, as well as latency remediation and improved user experiences.

SUMMARY OF THE PRESENT TECHNOLOGY

According to some embodiments, the present disclosure is directed to a secure messaging system, comprising: (a) a data retention and predictive analytics systems, both of which are in secure isolation from a remainder of the secure messaging system; (b) a web services layer providing access to the data retention and predictive analytics systems providing a goal-based planning application; (c) an application server layer that: (d) provides a user-facing application that accesses the data retention and predictive analytics systems through the web services layer, the user-facing application being secured through use of a security token cached on a web browser that provides the user-facing application; and (e) performs asynchronous processing based on user interaction with a goal-based planning application that processes data from a plurality of user accounts.

According to some embodiments, the present disclosure is directed to a method, comprising: (a) providing, by an application server layer, a user-facing application that accesses a data retention and predictive analytics systems through a web services layer, the user-facing application being secured through use of a security token cached on a web browser that provides the user-facing application; establishing a security protocol or security token utilized between the application server layer and the web services layer that is different from the security token cached on the web browser; and performing asynchronous processing based on user interaction with a goal-based planning application that processes data from a plurality of user accounts.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, where like reference numerals refer to identical or functionally similar elements throughout the separate views, together with the detailed description below, are incorporated in and form part of the specification, and serve to further illustrate embodiments of concepts that include the claimed disclosure, and explain various principles and advantages of those embodiments.

The methods and systems disclosed herein have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

FIG. 1 is a schematic diagram of a computing architecture that includes a system constructed in accordance with the present disclosure.

FIG. 2 is a schematic layer diagram of an example system constructed in accordance with the present disclosure.

FIG. 3 is a flowchart of an example method of the present disclosure.

FIG. 4 is a flowchart of another example method of request batching and processing, and latency reduction.

FIG. 5 illustrates an exemplary computing system that may be used to implement embodiments according to the present technology.

DETAILED DESCRIPTION

Generally speaking, the present disclosure provides secure messaging platforms and methods that allow for custodial account creation and automated control thereof. These platforms and methods advantageously implement secure messaging features and latency compensation features which allow the user to have an uninterrupted and secure user experience. Example implementations according to the present disclosure allow these platforms to be used for account maintenance and modification. In sum, a user can interact with their profile or account securely and without latency. By way of example, a user can perform various operations on their account. These various operations may require data intensive operations by a backend system in response. These data/compute intensive operations, but for the solutions described herein, would result in latency or other similar deleterious effects that would decrease the user experience.

Additionally, these platforms can be built upon existing third-party systems or services and can provide secure access and messaging into and out of these third-party systems and services. The security features described herein can isolate both system components and data from unauthorized access.

Some embodiments allow components of the platform to operate as a robotic advisor that designs and automatically implements actions in response to goals for a user.

In some embodiments, the systems and methods herein can continually review a plurality of accounts for a user and selectively adjust actions for these accounts based on the stated goal(s). These systems and methods can utilize machine learning to model account data against goals and generate instruction sets in response to these analyses. The outcome of these analyses can be transmitted to a third-party service in order to adjust one or more of the plurality of accounts in order to achieve the goal(s). This is referred to generally as automated account rebalancing.

Thus, some of the systems and methods disclosed herein comprise a re-balancer that may implement iterative machine learning in order to execute auto-configuration of accounts to ensure that goal(s) will be achieved. In some embodiments, a third party rebalancing system or service can be utilized. The systems disclosed herein can also implement other digital services, such as a document signing service or educational services. These educational services can be delivered, for example, through a user-facing application or interface disclosed herein, through a client-side downloadable application or externally referenced or hosted blogs, video or other such similar mechanisms.

In various embodiments, the systems and methods disclosed herein can generate a complete and robust profile of a user based on what the user purchases, user behaviors related to financial decisions, and so forth. These types of data are aggregated from a plurality of accounts such as bank accounts, investment accounts, credit reports and accounts, credit card statements, and so forth—just to name a few.

In some embodiments, the systems and methods herein are configured to allow for the aggregation of many accounts for centralized control, functional area goal planning, advisor-related content distribution, account and goal reporting, and various notification features. In one or more embodiments, the systems of the present disclosure can evaluate the goals and assets of a user and generate digital content recommendations for the user. In these instances, digital analytics are used as a basis to recommend advisor content for the user. For example, the systems and methods select content based on what similarly situated users clicked on and consumed. These similarities are determined relative to similarities in user financial behavior, account similarities, and goal similarities—just to name a few.

The systems and methods can also leverage deep analytics across anonymized customer profiles and accounts in order to make informed decisions and instruction sets for re-balancing the user accounts. The systems can also automatically generate new suggestions for a user based on current or predicted probabilities and/or goal(s). For example, a system can suggest a more aggressive repayment schedule for a debt if the system determines that selective adjustments to investments will result in higher dividends that originally modeled or planned. These features are enabled because the system tracks goal progress over time, collecting, reanalyzing, and rebalancing accounts as needed. During these processes, the system can determine if goals can be achieved more quickly than initially expected based on the ever changing nature of the user's accounts, inputs (e.g., for example changes in life-events), income or expense patterns, and any combinations and permutations thereof.

According to some embodiments, the systems and methods herein implement security layers that utilize SSL (secure socket layer) and encryption. These features, in addition to the token-based transaction features described infra, provide solutions to problems that arise in extensible or modular computing environments, where systems are built on existing third party resources.

FIG. 1 is a schematic diagram of an example secure messaging system (hereinafter system 100) for practicing aspects of the present disclosure. The system 100 comprises a data retention system 102, a predictive analytics system 104, a web services layer 106 (also referenced as web service layer 106), and an application server layer 108 that provides, for example, modeling and predictive analytics.

In some embodiments, the data retention system 102 and predictive analytics system 104 are in secure isolation from a remainder of the secure messaging system 100 through a security protocol or layer that will be described in greater detail herein. The data retention system 102 can also provide additional services such as business logic, data analysis, risk model analysis, security, data privacy controls, data access controls, disaster recovery for data and web services—just to name a few.

In various embodiments, the system 100 comprises connections (either direct or indirect) to a plurality of user accounts that each comprises commercial (e.g., financial account, consumer, fiscal data, etc.) information regarding a user. In some embodiments, at least one of the plurality of user accounts comprises a custodial trading platform.

The web services layer 106 generally provides access to the data retention system 102. According to some embodiments, the application server layer 108 is configured to provide a user-facing application 110 that accesses the data retention and predictive analytics systems through the web services layer 106. In some embodiments, the user-facing application 110 is secured through use of a security token cached on a web browser 112 that provides the user-facing application 110.

In one or more embodiments, the application server layer 108 performs asynchronous processing based on user interaction with a goal-based planning application (referred to herein as a user-facing application/interface) that processes data from a plurality of user accounts. A goal-based planning application and/or services can reside and execute on the application server layer 108. In other embodiments, the goal-based planning application may reside with the predictive analytics system 104. In another embodiment, the goal-based planning application can be a client-side, downloadable application.

In some embodiments, the system 100 uses the data provided by the user and their accounts as input to modeling and creating an interactive model. A view of this is provided by a front end framework and rendering application provided in Javascript or another suitable format. The front end framework is cooperatively provided by the web services layer 106 and the application server layer 108.

Generally speaking, the system 100 provides a wrapped web service layer that is built on top of or otherwise integrates a third party service, such as Salesforce™. In one or more embodiments, the web service layer 106 facilitates account updates and rebalancing through the system 100 and provides for separation between scenario modeling and probability calculations (e.g., schema) and a controller that defines and enforces rules of the schema for a user.

According to some embodiments, the application server layer 108 delivers Javascript to the web browser 112 when the user logs into the system 100. The application server layer 108 is the location where services are brokered for the user. For example, when a user desires to open a goal to look at details of the goal, the application server layer 108 calls the web service layer 106 for goal data for the user.

As noted above, the systems of the present disclosure implement security features that involve the use of multiple security tokens to provide message security in the system 100. Again, the system 100, in some embodiments, is built upon a third party service, such as Heroku™ or Salesforce™. The multi-token security schema implemented in the system 100 reduces the likelihood that system data will be compromised or accessible to any of the third party resources that the system 100 uses or is built upon.

Security tokens are used between the web service layer 106 and application server layer 108. In some embodiments, security features are not continuous to the web browser 112. Thus, a second security layer or link is established between the web browser 112 and application server layer, 108. In one or more embodiments, a first security token is cached in the application server layer 108 between the web browser 112 and the application server layer 108.

In some embodiments, the system 100 implements an architected message bus 114. In an example usage, a client requests a refresh of their accounts and user interface through their web browser 112. Rather than performing the refresh, which could involve data intensive and/or compute or operational intensive procedures by the system 100, the message bus allows the request for refresh to be processed asynchronously by a batching process 116 and provides a means for allowing the web browser 112 to continue to display a user-facing application to the user, allowing the user to continue to access accounts, content, and other offerings without waiting on the system 100 to complete its refresh of the user accounts and so forth. Once the requested refresh is complete, the application 110 is informed by message on the message bus and can auto-refresh appropriate data in the browser 112

Again, because the system 100 can utilize numerous user accounts in order to generate probabilistic suggestions, recommend content, perform account rebalancing, and update goal(s) and plans, the system 100, if implemented without the message bus 114, might provide an unacceptable user experience. This unacceptable user experience could be due to latency caused by the background refresh operations, or other system related jitter, delay and/or latency caused by other factors.

Also, latency can be remediated at the user-facing application based on the manner with which the user-facing application is created and how the data that is displayed through the user-facing application is stored and updated. For example, data displayed on the user-facing application that changes frequently, such as stock quotes, can cause frequent and unwanted refreshing of the entire user-facing application and GUIs. The present disclosure provides a solution to this issue by separating what is displayed on the GUI with the actual underlying data. The underlying data displayed on the GUI of the user-facing application can be updated, as needed, on a segment-by-segment basis (could be defined as a zone of pixels on the display) at a granular level, rather than updating the entire GUI. That is, the GUI that renders the underlying data is programmatically separate from the underlying data cached by the client (e.g., device rendering the GUIs of the user-facing application). Due to this separation, when data being displayed on the GUI changes, re-rendering of the data is performed at a granular level, rather than at the page level. This process represents another example solution that remedies latency and improves user experiences with the user-facing application.

To facilitate these features, the web browser 112 will listen on the message bus 114 for an acknowledgement or other confirmation that the background processes to update the user account and/or the user-facing application have been completed by the application server layer 108. The user-facing application (or even part thereof) is updated as the system 100 completes its processing. This allows the user-facing application provided through the web browser 112 to be usable, but heavy lifting is being done transparently to the user by the application server layer 108. In sum, these features prevent or reduce latency issues even when an application provided through the web browser 112 is “busy.” For example, a re-balance request is executed transparently by the application server layer 108 and batch processing system 116. This type of transparent computing behavior by the system 100 allows for asynchronous operation (initiated from the application server layer 108 or message bus 114).

In some embodiments, a batch engine 116 is included in the system 100 and works in the background to process re-balance requests and coordinate a number of services. An example re-balance request would include an instance where a user selectively changes a goal, such as selecting that they would prefer to pay off a debt in five years rather than seven. The batch engine 116 will transparently orchestrate the necessary operations required by the application sever layer 108 in order to obtain data from user accounts, re-balance the user's goal(s), and if needed generate instruction packages. These instruction packages can be transmitted to third parties for automatic execution to re-balance the user's accounts and ensure that a new or updated goal(s) is achievable and has been implemented.

According to some embodiments, the batch engine 116 is configured to process requests transparently to a user so that the user can continue to use the user-facing application without disruption. For example, this transparent processing can occur when the application server layer 108 transmits a request to the web services layer 106 for data, and a time required for updating or retrieving the data meets or exceeds a threshold. For example, the threshold might specify that if the request will take more than five seconds to complete, then the batch engine 116 can process the request transparently. The selected threshold can be system configured.

In some embodiments, the application server layer 108 initiates an updating processes from input received through the user-facing application such as when a user logs into the system or when the user requests rebalancing. The application server layer 108 executes a plan in accordance with goal(s) and re-updates models and probabilities related to the goal(s), along with statuses and current account information for the user.

In general, the application server layer 108 is configured to broker requests for data through the web services layer 106. In some embodiments, security of data transmission through the system 100 is improved by use of multiple security tokens. In one embodiment a security token cached on the web browser 112 is different from a security protocol or security token utilized between the application server layer 108 and the web services layer 106.

In various embodiments, the user-facing application provided by the system 100 is configured to analyze the plurality of user accounts to determine if the plurality of user accounts are compliant with the goal-based plan. In response, the system 100 can automatically generate trade requests for execution by a custodial trading platform (third-party trading platform) based on deviations determined during analysis that indicate that the plurality of user accounts are not complaint with the goal-based plan. That is, if the user needs to re-balance their accounts or behaviors based on a determination that their current assets and/or behaviors will result in their goal(s) not being achieved, the system 100 can detect the underperforming parts of the user's accounts and recommend a remediating action that re-balances the accounts to ensure that the goal(s) is achieved.

Part of the process of achieving goals involves educating the end user. Thus, in some embodiments, the system 100 can maintain a repository of educational content related to goals that may be achieved using the system 100 such as debt elimination, savings, retirement, and so forth. The system 100 can survey other profiles of users that are similar in financial position, have similar behaviors to the user, and desire similar goals or outcomes. The system 100 can determine if these other anonymized users have achieved their goals and can recommend rebalancing in order to improve a likelihood that the system, if it implements the same or similar strategies, will also achieve the same or similar goal as the successful users. The system 100 can also use these analytics to suggest or recommend educational content to the end user. For example, if the system determines that many users who were ultimately successful in starting their own business successfully completed basic accounting educational modules offered by the system 100, the system 100 can suggest these or similar education modules for the user. Thus, the user-facing application is configured to suggest digital content for the user based on deep analytics of a plurality of anonymized user accounts and the goal-based plan of the user. Again, this analysis can be accomplished using anonymized information obtained from other users and their associated accounts, analytics, goals, plans, and outcomes.

In an example operation, the system 100 can interface with a plurality of third party services, such as a trading platform service 120A, a rebalancing service 120B, a digital document signing service 120C, a simulation and scenario service 120D, and financial data service 120E. In some embodiments, the batch engine 116 can be configured to communicate with the trading platform service 120A, the predictive analytics system 104, and the financial data service 120E. For example trading account files can be exchanged between the batch engine 116 and the trading platform service 120A, such as trading instruction sets (for automatically rebalancing user accounts), and account information.

Scenario modeling and/or goals can be updated between the batch engine 116 and the predictive analytics system 104, while account aggregation can be facilitated between the batch engine 116 and the financial data service 120E.

Financial modeling is performed in the system 100 at a variety of layers as noted above. The system 100 then provides these models and associated data at runtime to the simulation and scenario service 120D and utilize its algorithms, such as Montecarlo simulations, and utilize the output of the scenarios to project future growth of investments, probability of success, and other such financial metrics.

In general, the batch engine 116 provides services such as trading platform service alerts, financial data service updates, goal analysis and updates, and ACH (automatic clearing house) processing, and so forth.

As noted above, the application server layer 108 is configured to provide the Javascript that enables the user-facing application provided on the web browser 112. Application synchronization and asynchronous data processing are facilitated by between the application server layer 108 and the batch engine 116, using the message bus 114.

According to some embodiments, the system 100 facilitates various synchronization processes such as account opening using the trading platform service 120A and the digital document signing service 120C. Funding of an account can be facilitated from a user's bank to the trading platform service 120A. Account dates can be obtained as desired from the trading platform service 120A. The system can also assign model portfolios, execute rebalancing of accounts through the rebalancing service 120B, and automatically generate and analyze goals using the predictive analytics system 104. User accounts can be linked through the financial data service 120E. Data can also be stored and retrieved from the Salesforce™ repository on which the web services layer 106 is built. A portion of the security tokens used in the system 100 are generated at the third party service on which the web services layer 106 is built, as described in greater detail above.

In some embodiments, the application server layer 108 cooperates with the message bus 114 to provide transparent processing of requests from the user-facing application. This transparent processing allows the application server layer 108 to continue to service the user-facing application. Thus, the message bus 114 facilitates completion of requests in the background, while the user continues to utilize the user-facing application without latency, or with reduced or acceptable latency.

The message bus 114 can be used to provide various batch processes such as account data retrieval and updating, account funding, trading and rebalancing, goal analysis, linked account updating, storing and retrieval of data from the third party service, and account and transaction related alerts.

As noted above, the web service layer 106 is built on top of a third party service, such as Salesforce™. This third party service operates as a data store, provides security for stored data, and stores and executes business rules.

FIG. 2 illustrates a layered schematic representation of the system 200 in conjunction with various third party applications and services 202. Some of the third party applications and services 202 described above provide a base upon which the system 200 is built. A predictive analytic and machine learning layer 204 is included. In some embodiments, a security layer 206, which includes the dual security token features of the present disclosure are built upon the predictive analytic and machine learning layer 204. Various functionalities and services are implemented through the application server layer described above, such as goal planning, investment services, content delivery, account reporting, account aggregation, notifications, and client profiles. These are all accessible through the user-facing application 208.

In more detail, the third party service layer provides a third party service token. The system 200 implements its own session-based token when the client initiates a connection to the system. This session-based token identifies a session and can be used by the third party service to identify a user of the session. The security layer 206 acts as an intermediary providing, for example, a firewall that prevents data leakage from the system to the third party service and vice-versa. This security layer 206 prevents any subsystem (third party service or application) that is leveraged by the system from compromising the components of the system, such as the application server layer and the batch engine. This provides a solution to a separation of concerns paradigm created when one system is built on another, such as the system 100 being built upon a third party service. In one example, the web browser used by the client (e.g., end user) is considered one subsystem. The user has various accounts, for example, three banking accounts, and several credit card accounts. Authentication credentials for accessing these accounts can be stored in a token, such as the third party service token, which is not shared with or accessible to the web browser.

Furthermore, the use of a multi-token security protocol allows for the system to be modular inasmuch as the third party service can be removed and replaced without compromising the security of the system, due to the fact that authentication credentials are stored in the third party service token rather than the session based tokens used by the system during a user session.

In some embodiments, third party systems are integrated in a modular manner. Thus, these third party services can be exchanged or replaced as desired without affecting the security and integrity of the system 100. Credentials used to communicate with these third party systems are not identical to the ones used by a user to when accessing the system 100. These third party credentials used are token based, and tokens are refreshed periodically in a cache of the web browser.

In some embodiments, the system 200 can provide various functionalities such as dynamic goal model selection, content recommendations (e.g., educational content), goal and action recommendations, cohort analysis and recommendations, automated investing, and automated custodial accounts—just to name a few. With respect to dynamic goal model selection, the system 200 is configured to combine goal parameters (such as individual attributes for user accounts that ensure that a goal is met within a specified time frame), and a user profile to determine a model portfolio for accomplishing the goal(s). This functionality also monitors empirical account information over time and selectively adjusting or rebalancing accounts as goal parameters evolve. This can be performed at various increments of time, such as daily, weekly, or other time periods.

Content recommendations can be facilitated by analyzing metadata tags of educational content and mapping such content to a client profile and their goals. The system can then suggest and push relevant content to a user, as well as train a predictive engine to fine tune the recommendation for the best (most suitable for the user) content.

Goal and action recommendations can include actions for a client based on their user profile and associated goals. The system can also recommend goals based on a user profile and a current financial plan (schema), and predict a most likely next goal for the user.

Cohort analysis and recommendations can be provided when the system analyzes all client profiles and financial plans in the abstract (and anonymized) to determine best practices relative to general or specific demographics. The system can also leverage various cohort analyses to make recommendations to clients such as budgeting, saving, planning, and so forth. The system can also assign badges and benchmarks to clients based on comparisons with similar clients.

With respect to automated investing, the system is configured to utilize a dynamic mode selection for a suitable investment strategy based on stated goal(s). The system can automate saving through ACH deposits, and can re-balance models monthly. The system could also allow for tax lot harvesting at the tax lot level as appropriate for the user, as well as aggregate all accounts into a net-worth financial dashboard provided through the user-facing application.

The system can also automatically open new accounts for the user, as well as orchestrate funding and transaction reporting.

FIG. 3 is a flowchart of an example method of the present disclosure. The method generally comprises a step 302 of providing, by an application server layer, a user-facing application that accesses data retention and predictive analytics systems through a web services layer.

The method also includes a step 304 of securing the user-facing application through use of a security token cached on a web browser that provides the user-facing application.

In some embodiments, the method includes a step 306 of establishing a security protocol or security token utilized between the application server layer and the web services layer that is different from the security token cached on the web browser. This provides, as noted above, a separation of concerns and provides security enhancement that prevents compromising of the system by any of the subsystems or third party services/applications that are leveraged by the system.

Next, the method includes a step 308 of performing asynchronous processing based on user interaction with a goal-based planning application that processes data from a plurality of user accounts. This asynchronous processing through, for example, a batch engine, allows data processes such as account updating, account rebalancing, modeling, and so forth to occur transparently to the user. In some embodiments, the method can include asynchronous processing, such as generating automatic account creation, account modeling relative to goals, and automatic trading instruction set generation—just to name a few.

Referring now to FIG. 4, which includes a flowchart of an example method performed by a batch engine. This method can build upon the method of FIG. 3. In some embodiments, the method can include a step 310 of providing a batching service or engine coupled to the application server layer through a message bus, as well as a step 312 of transmitting, by the application server layer, a request to the web services layer for data and a time required for updating or retrieving the data meets or exceeds a threshold. If the threshold is exceeded, the method can include a step 314 of transparently processing, by the batching service, the request such that the user can continue to use the user-facing application without latency caused by processing the request affecting the user-facing application. This method can be integrated into the method illustrated in FIG. 3.

FIG. 5 is a diagrammatic representation of an example machine in the form of a computer system 1, within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein may be executed. In various example embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a portable music player (e.g., a portable hard drive audio device such as an Moving Picture Experts Group Audio Layer 3 (MP3) player), a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system 1 includes a processor or multiple processor(s) 5 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), and a main memory 10 and static memory 15, which communicate with each other via a bus 20. The computer system 1 may further include a video display 35 (e.g., a liquid crystal display (LCD)). The computer system 1 may also include an alpha-numeric input device(s) 30 (e.g., a keyboard), a cursor control device (e.g., a mouse), a voice recognition or biometric verification unit (not shown), a drive unit 37 (also referred to as disk drive unit), a signal generation device 40 (e.g., a speaker), and a network interface device 45. The computer system 1 may further include a data encryption module (not shown) to encrypt data.

The disk drive unit 37 includes a computer or machine-readable medium 50 on which is stored one or more sets of instructions and data structures (e.g., instructions 55) embodying or utilizing any one or more of the methodologies or functions described herein. The instructions 55 may also reside, completely or at least partially, within the main memory 10 and/or within the processor(s) 5 during execution thereof by the computer system 1. The main memory 10 and the processor(s) 5 may also constitute machine-readable media.

The instructions 55 may further be transmitted or received over a network via the network interface device 45 utilizing any one of a number of well-known transfer protocols (e.g., Hyper Text Transfer Protocol (HTTP)). While the machine-readable medium 50 is shown in an example embodiment to be a single medium, the term “computer-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-readable medium” shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the machine and that causes the machine to perform any one or more of the methodologies of the present application, or that is capable of storing, encoding, or carrying data structures utilized by or associated with such a set of instructions. The term “computer-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals. Such media may also include, without limitation, hard disks, floppy disks, flash memory cards, digital video disks, random access memory (RAM), read only memory (ROM), and the like. The example embodiments described herein may be implemented in an operating environment comprising software installed on a computer, in hardware, or in a combination of software and hardware.

One skilled in the art will recognize that the Internet service may be configured to provide Internet access to one or more computing devices that are coupled to the Internet service, and that the computing devices may include one or more processors, buses, memory devices, display devices, input/output devices, and the like. Furthermore, those skilled in the art may appreciate that the Internet service may be coupled to one or more databases, repositories, servers, and the like, which may be utilized in order to implement any of the embodiments of the disclosure as described herein.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the present disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the present disclosure. Exemplary embodiments were chosen and described in order to best explain the principles of the present disclosure and its practical application, and to enable others of ordinary skill in the art to understand the present disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

While this technology is susceptible of embodiment in many different forms, there is shown in the drawings and will herein be described in detail several specific embodiments with the understanding that the present disclosure is to be considered as an exemplification of the principles of the technology and is not intended to limit the technology to the embodiments illustrated.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the technology. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It will be understood that like or analogous elements and/or components, referred to herein, may be identified throughout the drawings with like reference characters. It will be further understood that several of the figures are merely schematic representations of the present disclosure. As such, some of the components may have been distorted from their actual scale for pictorial clarity.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular embodiments, procedures, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details.

Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” or “according to one embodiment” (or other phrases having similar import) at various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Furthermore, depending on the context of discussion herein, a singular term may include its plural forms and a plural term may include its singular form. Similarly, a hyphenated term (e.g., “on-demand”) may be occasionally interchangeably used with its non-hyphenated version (e.g., “on demand”), a capitalized entry (e.g., “Software”) may be interchangeably used with its non-capitalized version (e.g., “software”), a plural term may be indicated with or without an apostrophe (e.g., PE's or PEs), and an italicized term (e.g., “N+1”) may be interchangeably used with its non-italicized version (e.g., “N+1”). Such occasional interchangeable uses shall not be considered inconsistent with each other.

Also, some embodiments may be described in terms of “means for” performing a task or set of tasks. It will be understood that a “means for” may be expressed herein in terms of a structure, such as a processor, a memory, an I/O device such as a camera, or combinations thereof. Alternatively, the “means for” may include an algorithm that is descriptive of a function or method step, while in yet other embodiments the “means for” is expressed in terms of a mathematical formula, prose, or as a flow chart or signal diagram.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is noted at the outset that the terms “coupled,” “connected”, “connecting,” “electrically connected,” etc., are used interchangeably herein to generally refer to the condition of being electrically/electronically connected. Similarly, a first entity is considered to be in “communication” with a second entity (or entities) when the first entity electrically sends and/or receives (whether through wireline or wireless means) information signals (whether containing data information or non-data/control information) to the second entity regardless of the type (analog or digital) of those signals. It is further noted that various figures (including component diagrams) shown and discussed herein are for illustrative purpose only, and are not drawn to scale.

While specific embodiments of, and examples for, the system are described above for illustrative purposes, various equivalent modifications are possible within the scope of the system, as those skilled in the relevant art will recognize. For example, while processes or steps are presented in a given order, alternative embodiments may perform routines having steps in a different order, and some processes or steps may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or sub-combinations. Each of these processes or steps may be implemented in a variety of different ways. Also, while processes or steps are at times shown as being performed in series, these processes or steps may instead be performed in parallel, or may be performed at different times.

While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. The descriptions are not intended to limit the scope of the invention to the particular forms set forth herein. To the contrary, the present descriptions are intended to cover such alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims and otherwise appreciated by one of ordinary skill in the art. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments. 

What is claimed is:
 1. A secure messaging system configured by at least one processor to execute instructions stored in memory, the system comprising: a data retention system and a predictive analytics system, both of which are in secure isolation from a remainder of the secure messaging system; a web services layer providing access to the data retention and predictive analytics systems providing a goal-based planning application; an application server layer that: provides a user-facing application that accesses the data retention and predictive analytics systems through the web services layer, the user-facing application being secured through use of a security token cached on a web browser that provides the user-facing application; and performs asynchronous processing based on user interaction with the goal-based planning application that processes data from a plurality of user accounts; and a batching service, wherein the application server layer transmits a request to the web services layer for data, and a time required for updating or retrieving the data meets or exceeds a threshold, the request being processed by the batching service transparently to a user such that the user can continue to use the user-facing application without disruption.
 2. The system according to claim 1, wherein the application server layer is further configured to broker requests for data from the data retention and predictive analytics systems through the web services layer.
 3. The system according to claim 1, wherein the security token cached on the web browser is different from a security protocol or security token utilized between the application server layer and the web services layer.
 4. The system according to claim 1, further comprising a message bus that communicatively couples the batching service with the application server layer, the message bus being used to transmit the request.
 5. The system according to claim 1, wherein the data retention and predictive analytics systems comprise connections to the plurality of user accounts that each comprise commercial information regarding a user, wherein at least one of the plurality of user accounts comprises a custodial trading platform.
 6. The system according to claim 5, wherein the user-facing application is configured to perform deep analytics on the plurality of user accounts to create a goal-based plan for the user.
 7. The system according to claim 6, wherein the user-facing application is configured to: analyze the plurality of user accounts to determine if the plurality of user accounts are compliant with the goal-based plan; and automatically generate trade requests to be executed by the custodial trading platform based on deviations determined during analysis that indicate that the plurality of user accounts are not compliant with the goal-based plan.
 8. The system according to claim 6, wherein the user-facing application is configured to suggest digital content for the user based on the deep analytics of the plurality of user accounts and the goal-based plan.
 9. The system according to claim 5, wherein the user-facing application is configured to update an account of the user each time the user logs into the system.
 10. A method, comprising: providing, by an application server layer, a user-facing application that accesses a data retention system and a predictive analytics system through a web services layer, the user-facing application being secured through use of a security token cached on a web browser that provides the user-facing application; establishing a security protocol or security token utilized between the application server layer and the web services layer that is different from the security token cached on the web browser; providing a batching service; transmitting, by the application server layer, a request to the web services layer for data and a time required for updating or retrieving the data meets or exceeds a threshold; transparently processing, by the batching service, the request such that a user can continue to use the user-facing application without latency caused by processing the request affecting the user-facing application; and performing asynchronous processing, by the application server layer, based on user interaction with a goal-based planning application of the predictive analytics system that processes data from a plurality of user accounts.
 11. The method according to claim 10, further comprising brokering requests for data from the data retention and predictive analytics systems through the web services layer.
 12. The method according to claim 10, further comprising communicatively coupling the batching service with the application server layer through a message bus, the message bus being used to transmit the request.
 13. The method according to claim 10, wherein the data retention and predictive analytics systems comprise connections to the plurality of user accounts that each comprise commercial information regarding a user, wherein at least one of the plurality of user accounts comprises a custodial trading platform.
 14. The method according to claim 13, wherein the user-facing application is configured to perform deep analytics on the plurality of user accounts to create a goal-based plan for the user.
 15. The method according to claim 14, further comprising further configuring the user-facing application to: analyze the plurality of user accounts to determine if the plurality of user accounts are compliant with the goal-based plan; and automatically generate trade requests to be executed by the custodial trading platform based on deviations determined during analysis that indicate that the plurality of user accounts are not compliant with the goal-based plan.
 16. The method according to claim 14, further comprising further configuring the user-facing application to suggest digital content for the user based on the deep analytics of the plurality of user accounts and the goal-based plan.
 17. The method according to claim 13, further comprising configuring the user-facing application to update an account of the user each time the user logs into the system.
 18. A secure messaging system configured to utilize at least one processor to execute instructions stored in memory, the system comprising: a data retention system in secure isolation from a remainder of the secure messaging system; a web services layer providing access to the data retention system; a goal-based planning application or service that provides predictive analytics; an application server layer that: provides a user-facing application, the user-facing application being secured through use of a security token cached on a web browser that provides the user-facing application; and performs asynchronous processing based on user interaction with the goal-based planning application that processes data from a plurality of user accounts; and a batching service, wherein a request from the application server layer to the web services layer for data is processed by the batching service transparently to a user such that the user can continue to use the user-facing application without disruption. 